stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/messages/MessagesScreen.kt (1)

122-145: ⚠️ Potential issue | 🟠 Major

Allow callers to remove the title click target.

MessageListHeader only drops click semantics when onHeaderTitleClick == null, but MessagesScreen and DefaultTopBarContent still require a non-null lambda and default it to {}. After moving channel-info navigation to the avatar, this leaves the title as a dead clickable element. Make this callback nullable through this chain, and mirror that in ChatComponentFactory.MessageListHeader, so avatar-only screens can render a truly non-interactive title.

Based on learnings, "In GetStream/stream-chat-android, PRs against major version branches (e.g., v7) are allowed to introduce breaking public API changes."

Also applies to: 301-324

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/messages/MessagesScreen.kt`
around lines 122 - 145, MessagesScreen currently forces a non-null
onHeaderTitleClick by defaulting it to an empty lambda which prevents
MessageListHeader from being non-clickable; change the onHeaderTitleClick
parameter in MessagesScreen to be nullable (onHeaderTitleClick: ((channel:
Channel) -> Unit)? = null), propagate that nullable type into
DefaultTopBarContent's parameter and invocation (pass null through), and update
DefaultTopBarContent and any usages to accept a nullable lambda; then update
ChatComponentFactory.MessageListHeader's API to accept a nullable
onHeaderTitleClick and ensure MessageListHeader checks for null before adding
click semantics so screens wanting an inert title can pass null. Ensure all call
sites and defaults are adjusted accordingly.

stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/theme/ChatComponentFactory.kt (1)

682-703: ⚠️ Potential issue | 🟡 Minor

Add changelog entry for MessageListHeader and MessageListHeaderTrailingContent callback signature changes.

The ChatComponentFactory extension points for MessageListHeader and MessageListHeaderTrailingContent now require callbacks with (Channel) -> Unit signatures, breaking custom implementations. This change must be documented in CHANGELOG.md under the stream-chat-android-compose section with a breaking change marker (🚨) explaining the signature updates and migration path for SDK consumers.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/theme/ChatComponentFactory.kt`
around lines 682 - 703, Add a breaking change entry to CHANGELOG.md under the
stream-chat-android-compose section documenting that the ChatComponentFactory
extension points MessageListHeader and MessageListHeaderTrailingContent now
require callbacks with the signature (Channel) -> Unit; include the 🚨 marker, a
short description of the change (old vs new signature), and a migration note
telling consumers to update their custom implementations to accept a Channel
parameter (e.g., change handlers passed into MessageListHeader and
MessageListHeaderTrailingContent to (channel: Channel) -> Unit) and any sample
before/after usage to make the migration clear.